| From: | Richard Mattsson |
| Date: | 16 May 2000 at 19:02:57 |
| Subject: | HDToolBox Issues (was: dkbscsi.device) |
Hi, folks! I just wanted to share my experience getting a 'new' 4.3 Gig
SCSI HD up under OS3.5.
I've been following the thread regarding HDToolBox not recognizing
unprepped drives.
Janne Karppanen <janne.karppanen@quicknet.inet.fi> wrote:
> Subject: Re: 3.5 Inch IDE drive install
> DC> As you say, we now need to narrow it down. Perhaps it recognises
> DC> SCSI drives but not IDE?
> OS3.5 HDtoolbox (v44.22) recognised my Seagate 8.4 GB IDE-drive :-)
Well, in my case, HDToolBox recognized the drive just fine. But
partitioning it presented the same problem Jay experienced:
"Jay" <jayhanan@caltech.edu> wrote:
> Subject: dkbscsi.device
> when I run a program like the HDTool Box the IBM hard
> drive does show up as something I can partition, but the partitions
> never show up for formatting. Can you suggest a solution?
Yes, *none* of the paritions I created with HDToolBox would show up for
formatting after a reboot. (HDToolbox 44.22 - BB1)
(The drive is an IBM Ultrastar DDRS-34560 -
http://ssdweb01.storage.ibm.com/techsup/hddtech/ddrs/ddrsdes.htm
I'm using a 2091 controller with GuruROM, version 1.13, which supports
the TD64 command in NSDPatch.config...)
My first solution was to use HDToolbox 40.4 which I had from 3.1. This
made it possible to create partitions which I could format afterward. I
didn't partition it past the 4G limit, though. Later I went back with
HDToolbox 44.22 and re-partitioned the drive to use the full capacity.
There was still some odd behavior with the last partition, and someone
advised me to try HDInstTools instead. This would probably be the best
advice for Jay at this point, though I really like the draggable
partition GUI in the new HDToolBox. (Making one of the first partitions
BIGGER in HDInstTools is a PITA - I just had to delete all the
partitions above it and re-create them...)
HDInstTools -
http://www.elaborate-bytes.com
However, my last parition still refuses to auto-mount. As an
alternative, I've tried using the ACTIVATE switch in the NSDPatch.config
line for my controller, but it still doesn't work. The partition shows
up in early startup Boot Options, and is accessible with Mounter and is
listed when issuing an Assign command. In fact, since I plan to use this
partition for temp storage, it isn't a problem, and I've just made a
TEMP: assign to it and everything's fine. I was nervous about the
possibility of a problem with >4G support, but I've fully formatted and
completely filled the last partition with no problems, after a full
backup, of course! It's just strange...
------------------------------------------------------------------------
Accurate impartial advice on everything from laptops to table saws.
http://click.egroups.com/1/3020/3/_/644178/_/958500835/
------------------------------------------------------------------------